Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTPS test for sharded shuffle #1473

Merged

Conversation

akoshelev
Copy link
Collaborator

This almost completes the setup for TLS/encryption infrastructure with one major exception - match key encryption keys are not re-used across shards. I have a PR almost ready, but decided to split that functionality to make PR somewhat revieweable

This almost completes the setup for TLS/encryption infrastructure
with one major exception - match key encryption keys are not re-used
across shards. I have a PR almost ready, but decided to split that
functionality to make PR somewhat revieweable
@akoshelev akoshelev force-pushed the https-sharded-shuffle-test-2 branch from 8db537b to 4f0296f Compare December 4, 2024 05:46
Copy link

codecov bot commented Dec 4, 2024

Codecov Report

Attention: Patch coverage is 98.70130% with 1 line in your changes missing coverage. Please review.

Project coverage is 93.84%. Comparing base (cf7efd4) to head (a950026).
Report is 8 commits behind head on main.

Files with missing lines Patch % Lines
ipa-core/src/cli/clientconf.rs 75.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1473      +/-   ##
==========================================
- Coverage   93.86%   93.84%   -0.02%     
==========================================
  Files         235      235              
  Lines       42451    42438      -13     
==========================================
- Hits        39845    39826      -19     
- Misses       2606     2612       +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Collaborator

@cberkhoff cberkhoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What changed in sharded_keygen or is it more of a cosmetical change?

@@ -189,18 +185,39 @@ pub fn spawn_shards(
.args(["-i", &id.to_string()])
.args(["--shard-index", &shard_index.to_string()])
.args(["--shard-count", &shard_count.to_string()])
.args(["--network".into(), config_path.join("network.toml")])
.arg("--disable-https")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so this is the first time we have https tests?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for sharded world yes

@akoshelev
Copy link
Collaborator Author

What changed in sharded_keygen or is it more of a cosmetical change?
yea, more code re-use and less copy-paste

@akoshelev akoshelev merged commit 3cba381 into private-attribution:main Dec 4, 2024
12 checks passed
@akoshelev akoshelev deleted the https-sharded-shuffle-test-2 branch December 4, 2024 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants